Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 10, 2024

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ~3.8.3~3.9.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v3.9.10: TypeScript 3.9.10

Compare Source

This release ships both an overall performance improvement, along with a mitigation for a performance regression when upgrading to Node.js 16. See the change for more details.

v3.9.9: TypeScript 3.9.9

Compare Source

This release contains a fix for an issue when language service plugins have no specified name.

v3.9.8: TypeScript 3.9.8

Compare Source

This release contains fixes for a security risk involving language service plugin loading. More details are available here.

v3.9.7: TypeScript 3.9.7

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

This release contains a fix for CVE-2020-1416

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.6: TypeScript 3.9.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.5: TypeScript 3.9.5

This release contains bug fixes in type-checking, emit, and editor scenarios.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.3: TypeScript 3.9.3

Compare Source

This release contains bug fixes in type-checking, APIs, emit, and editor scenarios.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.9.2: TypeScript 3.9.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Feb 10, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular-devkit/build-angular@0.901.1
npm ERR! Found: typescript@3.9.10
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~3.9.0" from the root project
npm ERR!   typescript@"^3.6.3" from @biesbjerg/ngx-translate-extract@4.2.0
npm ERR!   node_modules/@biesbjerg/ngx-translate-extract
npm ERR!     dev @biesbjerg/ngx-translate-extract@"^4.2.0" from the root project
npm ERR!   4 more (@phenomnomnominal/tsquery, ts-node, tslint, tsutils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=3.6 < 3.9" from @angular-devkit/build-angular@0.901.1
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"^0.901.0" from the root project
npm ERR!   peer @angular-devkit/build-angular@">=0.801.0" from @angular-builders/jest@8.3.2
npm ERR!   node_modules/@angular-builders/jest
npm ERR!     dev @angular-builders/jest@"^8.3.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@3.8.3
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=3.6 < 3.9" from @angular-devkit/build-angular@0.901.1
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"^0.901.0" from the root project
npm ERR!     peer @angular-devkit/build-angular@">=0.801.0" from @angular-builders/jest@8.3.2
npm ERR!     node_modules/@angular-builders/jest
npm ERR!       dev @angular-builders/jest@"^8.3.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-10T10_01_44_696Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-10T10_01_44_696Z-debug-0.log

@vercel
Copy link

vercel bot commented Feb 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
outlet ❌ Failed (Inspect) Aug 10, 2025 2:31pm

@renovate renovate bot force-pushed the renovate/typescript-3.x branch from cfde6c2 to 0ba576f Compare August 10, 2025 14:29
@renovate
Copy link
Contributor Author

renovate bot commented Aug 10, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular-devkit/build-angular@0.901.1
npm error Found: typescript@3.9.10
npm error node_modules/typescript
npm error   dev typescript@"~3.9.0" from the root project
npm error   typescript@"^3.6.3" from @biesbjerg/ngx-translate-extract@4.2.0
npm error   node_modules/@biesbjerg/ngx-translate-extract
npm error     dev @biesbjerg/ngx-translate-extract@"^4.2.0" from the root project
npm error   4 more (@phenomnomnominal/tsquery, ts-node, tslint, tsutils)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=3.6 < 3.9" from @angular-devkit/build-angular@0.901.1
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"^0.901.0" from the root project
npm error   peer @angular-devkit/build-angular@">=0.801.0" from @angular-builders/jest@8.3.2
npm error   node_modules/@angular-builders/jest
npm error     dev @angular-builders/jest@"^8.3.2" from the root project
npm error
npm error Conflicting peer dependency: typescript@3.8.3
npm error node_modules/typescript
npm error   peer typescript@">=3.6 < 3.9" from @angular-devkit/build-angular@0.901.1
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"^0.901.0" from the root project
npm error     peer @angular-devkit/build-angular@">=0.801.0" from @angular-builders/jest@8.3.2
npm error     node_modules/@angular-builders/jest
npm error       dev @angular-builders/jest@"^8.3.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-01-23T16_37_23_210Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-23T16_37_23_210Z-debug-0.log

@coderabbitai
Copy link

coderabbitai bot commented Aug 10, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants